<html>
<head><meta charset="utf-8"><title>check-in at T-compiler mtg · t-compiler/rust-analyzer · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/index.html">t-compiler/rust-analyzer</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html">check-in at T-compiler mtg</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="159428410"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159428410" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pnkfelix <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159428410">(Feb 26 2019 at 14:38)</a>:</h4>
<p>hey <span class="user-mention" data-user-id="133169">@matklad</span> , are you available during the compiler triage meeting this Thursday (15:00 - 16:00 UTC)?</p>



<a name="159428458"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159428458" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pnkfelix <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159428458">(Feb 26 2019 at 14:39)</a>:</h4>
<p><span class="user-mention" data-user-id="116009">@nikomatsakis</span> and I were thinking it would be great for the WG-rls-2.0 to be part of this week "Working Group check-in", especially to get feedback on the short-term planning we have sketched out so far</p>



<a name="159428478"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159428478" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159428478">(Feb 26 2019 at 14:39)</a>:</h4>
<p>(cc <span class="user-mention" data-user-id="153740">@Igor Matuszewski</span>)</p>



<a name="159428564"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159428564" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pnkfelix <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159428564">(Feb 26 2019 at 14:40)</a>:</h4>
<p>and I was thinking that if you (or <span class="user-mention" data-user-id="153740">@Igor Matuszewski</span> , yes)  were available, even just for the 15:30 -- 16:00 UTC portion of the meeting, then having one of you drive the presentation would be great</p>



<a name="159428649"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159428649" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159428649">(Feb 26 2019 at 14:41)</a>:</h4>
<p>In particular I was thinking it would be good to "broadcast" the <a href="#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/roadmap.20sketch.20call/near/159370246" title="#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/roadmap.20sketch.20call/near/159370246">overall theme we seemed to have arrived at yesterday</a>, and that the compiler time might be able to help sharpen the "it would be useful to exclude this part of Rust to simplify things".</p>
<p>(Actually, on that note, I think it would be great to run some of those thoughts by <span class="user-mention" data-user-id="123856">@Vadim Petrochenkov</span>, not sure if they'll be present at the meeting...)</p>



<a name="159432606"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159432606" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Vadim Petrochenkov <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159432606">(Feb 26 2019 at 15:32)</a>:</h4>
<p>Random thoughts:<br>
- Most of code in <code>librustc_resolve</code> is about diagnostics at this point.<br>
- I'd like to have a standalone model that's "pure",  simplified, formalized and doesn't have all that diagnostic cruft and language features irrelevant to resolution.<br>
- I'm unlikely to work on such a model.<br>
- That standalone model probably won't be directly reusable in rustc due to diagnostics, and its source will need to be expanded and integrated in rustc.<br>
- I'm generally unhappy about the compiler moving from the "monorepo" model to separate crates, repos, organizations.<br>
- My preferences can probably be ignored since I'm unlikely to participate in the rls 2.0 / frontend 2.0 work in any significant capacity.</p>



<a name="159433530"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159433530" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pnkfelix <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159433530">(Feb 26 2019 at 15:45)</a>:</h4>
<p>Hmm. I admit I had not given much proper thought as to how to architect diagnostic-support if we do indeed try to make the model directly testable in rustc itself</p>



<a name="159433610"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159433610" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pnkfelix <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159433610">(Feb 26 2019 at 15:46)</a>:</h4>
<p>but I certainly agree that if it doesn't have diagnostic support, then there's no way rustc could switch to it as the primary implementation.</p>



<a name="159437351"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159437351" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159437351">(Feb 26 2019 at 16:35)</a>:</h4>
<p>yup, added to my calendar.</p>
<blockquote>
<p>I'm generally unhappy about the compiler moving from the "monorepo" model to separate crates, repos, organizations.</p>
</blockquote>
<p>My personal end goal is a monorepo setup, but a monorepo of fairly independent libraries. I see the current setup with a separate repo as a temporary one.</p>



<a name="159437469"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159437469" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159437469">(Feb 26 2019 at 16:36)</a>:</h4>
<p>Will also prepare the summary document for the yesterday's discussion by thursday</p>



<a name="159445331"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159445331" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159445331">(Feb 26 2019 at 18:28)</a>:</h4>
<blockquote>
<ul>
<li>I'm generally unhappy about the compiler moving from the "monorepo" model to separate crates, repos, organizations.</li>
</ul>
</blockquote>
<p>On this note, leaving aside the mono/poly-repo question (which is very technical), I think that the goal of working <em>groups</em> (i.e., the "organizations" part of your sentence) is really to allow us to scale and do more things <strong>without</strong> fragmenting too much. That is, a key point is to find ways to keep us all aware of what's going on (to the extent we wish to follow along). If that's not working, we should definitely tinker with the model.  (I would say it's too early to tell this as of yet, since we're not really "up and running" yet)</p>



<a name="159464691"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159464691" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> centril <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159464691">(Feb 26 2019 at 22:28)</a>:</h4>
<blockquote>
<ul>
<li>I'd like to have a standalone model that's "pure", simplified, formalized and doesn't have all that diagnostic cruft and language features irrelevant to resolution.</li>
</ul>
</blockquote>
<p><span aria-label="heart" class="emoji emoji-2764" role="img" title="heart">:heart:</span> ; I think we should aspire to this for most of the things in the language including syntax (lexical + abstract), resolution, traits, type system, abstract machine, etc.</p>



<a name="159620780"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159620780" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159620780">(Feb 28 2019 at 14:59)</a>:</h4>
<p>Is the meeting on IRC?</p>



<a name="159620874"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/185405-t-compiler/rust-analyzer/topic/check-in%20at%20T-compiler%20mtg/near/159620874" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> matklad <a href="https://rust-lang.github.io/zulip_archive/stream/185405-t-compiler/rust-analyzer/topic/check-in.20at.20T-compiler.20mtg.html#159620874">(Feb 28 2019 at 15:00)</a>:</h4>
<p>Calendar says: "The meeting occurs in #rustc on IRC." I thought we've moved off of IRC?</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>